Methods, terminal device and network node for uplink transmission

ABSTRACT

Methods, a terminal device and a network node for uplink transmission, in which the terminal device transmits a transport block (TB) to a network node with a first configured grant. The terminal device retransmits the TB to the network node autonomously with a second configured grant.

TECHNICAL FIELD

Embodiments of the disclosure generally relate to wirelesscommunication, and, more particularly, to methods, a terminal device anda network node for uplink transmission.

BACKGROUND

This section introduces aspects that may facilitate better understandingof the present disclosure. Accordingly, the statements of this sectionare to be read in this light and are not to be understood as admissionsabout what is in the prior art or what is not in the prior art.

The 5th generation of cellular system, called new radio (NR) isdeveloped for maximum flexibility to support multiple and substantiallydifferent use cases. Besides the typical mobile broadband use case,there are also machine type communication (MTC), ultra-low latencycritical communications (ULLCC), side-link device-to-device (D2D) andseveral other use cases.

In NR, the basic scheduling unit is called a slot. A slot consists of 14orthogonal frequency division multiplexing (OFDM) symbols for the normalcyclic prefix configuration. NR supports many different subcarrierspacing (SCS) configurations and at an SCS of 30 kHz the OFDM symbolduration is about 33 μs. As an example, a slot with 14 symbols for thesame SCS is 500 μs long (including cyclic prefixes).

NR also supports flexible bandwidth configurations for different userequipments (UEs) on the same serving cell. In other words, the bandwidthmonitored by a UE and used for its control and data channels may besmaller than the carrier bandwidth. One or multiple bandwidth part (BWP)configurations for each component carrier can be semi-staticallysignaled to a UE, where a BWP consists of a group of contiguous physicalresource blocks (PRBs). Reserved resources can be configured within theBWP. The bandwidth of a BWP equals to or is smaller than the maximalbandwidth capability supported by a UE.

NR is targeting both licensed and unlicensed bands. Allowing unlicensednetworks, i.e., networks that operate in shared spectrum (or unlicensedspectrum) to effectively use the available spectrum is an attractiveapproach to increase system capacity. Although unlicensed spectrum doesnot match the qualities of the licensed regime, solutions that allow anefficient use of it as a complement to licensed deployments have thepotential to bring great value to the 3rd generation partnership project(3GPP) operators, and, ultimately, to the 3GPP industry as a whole. Itis expected that some features in NR will need to be adapted to complywith the special characteristics of the unlicensed band as well as alsodifferent regulations. An SCS of 15 kHz or 30 kHz are the most promisingcandidates for NR-based access to unlicensed spectrum (NR-U) OFDMnumerologies for frequencies below 6 GHz.

When operating in unlicensed spectrum, many regions in the world requirea device to sense the medium as free before transmitting. This operationis often referred to as listen before talk or LBT for short. It isdesigned for unlicensed spectrum co-existence with other radio accesstechnologies (RATs). For this mechanism in NR unlicensed spectrum, aradio device applies a clear channel assessment (CCA) check (i.e.channel sensing) before any transmission. The transmitter involvesenergy detection (ED) over a time period compared to a certain threshold(ED threshold) in order to determine if a channel is idle. In case thechannel is determined to be occupied, the transmitter performs a randomback-off within a contention window before next CCA attempt. In order toprotect the acknowledgement (ACK) transmissions, the transmitter mustdefer a period after each busy CCA slot prior to resuming back-off. Assoon as the transmitter has grasped access to a channel, the transmitteris only allowed to perform transmission up to a maximum time duration(namely, the maximum channel occupancy time (MCOT)). For quality ofservice (QoS) differentiation, a channel access priority based on theservice type has been defined. For example, there are four LBT priorityclasses defined for differentiation of contention window sizes (CWS) andMCOT between services.

There are many different flavors of LBT, depending on which radiotechnology the device uses and which type of data it wants to transmitat the moment. Common for all flavors is that the sensing is done in aparticular channel (corresponding to a defined carrier frequency) andover a predefined bandwidth. For example, in the 5 GHz band, the sensingis done over 20 MHz channels.

Many devices are capable of transmitting (and receiving) over a widebandwidth including multiple sub-bands/channels, e.g., LBT sub-band(i.e., the frequency part with bandwidth equals to LBT bandwidth). Adevice is only allowed to transmit on the sub-bands where the medium issensed as free. Again, there are different flavors of how the sensingshould be done when multiple sub-bands are involved.

In principle, there are two ways a device can operate over multiplesub-bands. One way is that the transmitter/receiver bandwidth is changeddepending on which sub-bands that were sensed as free. In this setup,there is only one component carrier (CC) and the multiple sub-bands aretreated as single channel with a larger bandwidth. The other way is thatthe device operates almost independent processing chains for eachchannel. Depending on how independent the processing chains are, thisoption can be referred to as either carrier aggregation (CA) or dualconnectivity (DC).

SUMMARY

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the detaileddescription. This summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter.

One of the objects of the disclosure is to provide an improved solutionfor uplink transmission.

According to a first aspect of the disclosure, there is provided amethod in a terminal device. The method may comprise transmitting atransport block (TB) to a network node with a first configured grant.The method may further comprise retransmitting the TB to the networknode autonomously with a second configured grant.

In an embodiment of the disclosure, the autonomous retransmission of theTB may stop when a timer whose timer value equals a predeterminedmaximum time period expires.

In an embodiment of the disclosure, the second configured grant maybelong to a first configured grant configuration. The method may furthercomprise retransmitting the TB to the network node autonomously with athird configured grant belonging to a second configured grantconfiguration.

In an embodiment of the disclosure, the second configured grant maybelong to a first configured grant configuration. The method may furthercomprise retransmitting the TB to the network node autonomously with athird configured grant belonging to the first configured grantconfiguration.

In an embodiment of the disclosure, the first configured grant maybelong to the first or second configured grant configuration.

In an embodiment of the disclosure, the first configured grant maybelong to a third configured grant configuration.

In an embodiment of the disclosure, the TB may be transmitted with ahybrid automatic repeat request (HARQ) process.

In an embodiment of the disclosure, the autonomous retransmission of theTB may be performed one or more times with the same HARQ process.

In an embodiment of the disclosure, the timer may be started at a timepoint related to the transmission of the TB.

In an embodiment of the disclosure, the timer may be stopped when theterminal device receives an acknowledgement for the TB.

In an embodiment of the disclosure, a size of the TB may be determinedbased on the first, second or third configured grant configuration.

In an embodiment of the disclosure, the first, second or thirdconfigured grant configuration may be received from the network node.

In an embodiment of the disclosure, the TB may be retransmittedautonomously with the second configured grant when the terminal devicedetermines that an autonomous retransmission with the second configuredgrant is allowed.

In an embodiment of the disclosure, the autonomous retransmission of theTB may be performed multiple times. A first part of the multipleautonomous retransmissions may be performed with the same HARQ processand a second part of the multiple autonomous retransmissions may beperformed with another HARQ process.

In an embodiment of the disclosure, the another HARQ process may be usedwhen the terminal device has not received any HARQ feedback for the TBafter a predetermined number of transmission attempts or a predeterminedtime period.

In an embodiment of the disclosure, the second configured grant maybelong to a first configured grant configuration. The method may furthercomprise retransmitting the TB to the network node autonomously with thesecond and third configured grants.

In an embodiment of the disclosure, the autonomous retransmission of theTB may stop when a predetermined maximum number of transmission attemptsis reached or a predetermined maximum time period has elapsed.

In an embodiment of the disclosure, the predetermined maximum number oftransmission attempts or the predetermined maximum time period may bebased on a latency requirement of related service data or related one ormore logical channels.

In an embodiment of the disclosure, the method may further comprise,when the terminal device has not received an acknowledgement for the TBafter the predetermined maximum number of transmission attempts isreached or the predetermined maximum time period has elapsed,transmitting a failure report for the TB to the network node.

In an embodiment of the disclosure, the transmission attempts maycontain one or more transmission attempts missed due to LBT failure.

In an embodiment of the disclosure, the predetermined maximum timeperiod may contain time elapsed for one or more LBT operations.

In an embodiment of the disclosure, when the predetermined maximumnumber of transmission attempts is to be reached or the predeterminedmaximum time period is to elapse, the autonomous retransmission of theTB may be performed proactively.

In an embodiment of the disclosure, the autonomous retransmission of theTB may be performed proactively by performing the autonomousretransmission of the TB without waiting a feedback for the TB orwithout waiting an expiration of a configured grant retransmissiontimer. The expiration of the configured grant retransmission timer maybe used to trigger an autonomous retransmission using a configuredgrant.

In an embodiment of the disclosure, the timer may be stopped when theterminal device receives a dynamic grant for retransmission of the TB.

In an embodiment of the disclosure, the timer may be started when one offollowing events occurs: a media access control (MAC) protocol data unit(PDU) corresponding to the TB has been generated; a first LBT operationis started for a first transmission attempt of the TB; and a firstpotential transmission opportunity for the TB occurs.

In an embodiment of the disclosure, a configured grant timer may bereused as the timer.

In an embodiment of the disclosure, the method may further compriseindicating, to the network node, a number of transmission attempts forthe TB or delay experienced for the transmissions of the TB.

In an embodiment of the disclosure, the number of the transmissionattempts or the experienced delay may be indicated by one or more of:redundant version of the TB; uplink control information (UCI); radioresource control (RRC) signaling; MAC control element (CE); and Layer 1or Layer 2 signaling.

In an embodiment of the disclosure, the method may further comprisereceiving a signaling indicating termination of retransmissions for theTB.

In an embodiment of the disclosure, the method may further comprise, inresponse to the signaling, triggering upper layer retransmissions of thedata corresponding to the TB.

In an embodiment of the disclosure, the method may further compriseproviding user data and forwarding the user data to a host computer viathe transmission to the base station.

According to a second aspect of the disclosure, there is provided amethod in a network node. The method may comprise receiving, from aterminal device, information related to one or more autonomous uplinkretransmissions of a TB with one or more configured grants. The methodmay further comprise determining a scheduling policy or a schedulingdecision for the TB based on the information.

In an embodiment of the disclosure, the method may further comprisetransmitting one or more configured grant configurations to the terminaldevice.

In an embodiment of the disclosure, the scheduling policy may bedetermined to ensure the retransmissions from the terminal device to becompleted within a predetermined maximum time period.

In an embodiment of the disclosure, the scheduling decision may indicatetermination of retransmissions for the TB.

In an embodiment of the disclosure, the method may further comprisesending a signaling indicating the scheduling decision to the terminaldevice.

In an embodiment of the disclosure, the signaling may be sent as one ormore of: a Layer 1/Layer 2 signaling; a MAC CE; and an RRC signaling.

In an embodiment of the disclosure, the information may comprise one ormore of: a number of transmission attempts for the TB or delayexperienced for the transmissions of the TB; a HARQ process identifierfor the TB; and a failure indication that the TB is not to beretransmitted autonomously from the terminal device.

In an embodiment of the disclosure, the scheduling policy may compriseone or more of: scheduling priority for the TB; parameters for physicaldownlink control channel (PDCCH) carrying an uplink grant forretransmission of the TB; physical uplink shared channel (PUSCH)duration length for the TB; transmission power parameters for the TB;and PUSCH preparation delay for the TB.

In an embodiment of the disclosure, the method may further comprisetransmitting, to a terminal device, information indicating apredetermined maximum number of transmission attempts or a predeterminedmaximum time period. The autonomous retransmission of a TB may stop whenthe predetermined maximum number of transmission attempts is reached orthe predetermined maximum time period has elapsed.

In an embodiment of the disclosure, the predetermined maximum number oftransmission attempts or the predetermined maximum time period may bebased on a latency requirement of related service data or related one ormore logical channels.

According to a third aspect of the disclosure, there is provided aterminal device. The terminal device may comprise at least one processorand at least one memory. The at least one memory may containinstructions executable by the at least one processor, whereby theterminal device may be operative to transmit a TB to a network node witha first configured grant. The terminal device may be further operativeto retransmit the TB to the network node autonomously with a secondconfigured grant.

In an embodiment of the disclosure, the terminal device may be operativeto perform the method according to the above first aspect.

According to a fourth aspect of the disclosure, there is provided anetwork node. The network node may comprise at least one processor andat least one memory. The at least one memory may contain instructionsexecutable by the at least one processor, whereby the network node maybe operative to receive, from a terminal device, information related toone or more autonomous uplink retransmissions of a TB with one or moreconfigured grants. The network node may be further operative todetermine a scheduling policy or a scheduling decision for the TB basedon the information.

In an embodiment of the disclosure, the network node may be operative toperform the method according to the above second aspect.

According to a fifth aspect of the disclosure, there is provided acomputer program product. The computer program product may compriseinstructions which when executed by at least one processor, cause the atleast one processor to perform the method according to any of the abovefirst and second aspects.

According to a sixth aspect of the disclosure, there is provided acomputer readable storage medium. The computer readable storage mediummay comprise instructions which when executed by at least one processor,cause the at least one processor to perform the method according to anyof the above first and second aspects.

According to a seventh aspect of the disclosure, there is provided aterminal device. The terminal device may comprise a transmission modulefor transmitting a TB to a network node with a first configured grant.The terminal device may further comprise a retransmission module forretransmitting the TB to the network node autonomously with a secondconfigured grant.

According to an eighth aspect of the disclosure, there is provided anetwork node. The network node may comprise a reception module forreceiving, from a terminal device, information related to one or moreautonomous uplink retransmissions of a TB with one or more configuredgrants. The network node may further comprise a determination module fordetermining a scheduling policy or a scheduling decision for the TBbased on the information.

According to a ninth aspect of the disclosure, there is provided amethod implemented in a communication system including a host computer,a base station and a terminal device. The method may comprise, at thehost computer, receiving user data transmitted to the base station fromthe terminal device. The terminal device may transmit a TB to the basestation with a first configured grant. The terminal device mayretransmit the TB to the base station autonomously with a secondconfigured grant.

In an embodiment of the disclosure, the method may further comprise, atthe terminal device, providing the user data to the base station.

In an embodiment of the disclosure, the method may further comprise, atthe terminal device, executing a client application, thereby providingthe user data to be transmitted. The method may further comprise, at thehost computer, executing a host application associated with the clientapplication.

In an embodiment of the disclosure, the method may further comprise, atthe terminal device, executing a client application. The method mayfurther comprise, at the terminal device, receiving input data to theclient application. The input data may be provided at the host computerby executing a host application associated with the client application.The user data to be transmitted may be provided by the clientapplication in response to the input data.

According to a tenth aspect of the disclosure, there is provided acommunication system including a host computer comprising acommunication interface configured to receive user data originating froma transmission from a terminal device to a base station. The terminaldevice may comprise a radio interface and processing circuitry. Theprocessing circuitry of the terminal device may be configured totransmit a TB to the base station with a first configured grant. Theprocessing circuitry of the terminal device may be further configured toretransmit the TB to the base station autonomously with a secondconfigured grant.

In an embodiment of the disclosure, the communication system may furtherinclude the terminal device.

In an embodiment of the disclosure, the communication system may furtherinclude the base station. The base station may comprise a radiointerface configured to communicate with the terminal device and acommunication interface configured to forward to the host computer theuser data carried by a transmission from the terminal device to the basestation.

In an embodiment of the disclosure, the processing circuitry of the hostcomputer may be configured to execute a host application. The processingcircuitry of the terminal device may be configured to execute a clientapplication associated with the host application, thereby providing theuser data.

In an embodiment of the disclosure, the processing circuitry of the hostcomputer may be configured to execute a host application, therebyproviding request data. The processing circuitry of the terminal devicemay be configured to execute a client application associated with thehost application, thereby providing the user data in response to therequest data.

According to an eleventh aspect of the disclosure, there is provided amethod implemented in a communication system including a host computer,a base station and a terminal device. The method may comprise, at thehost computer, receiving, from the base station, user data originatingfrom a transmission which the base station has received from theterminal device. The base station may receive, from a terminal device,information related to one or more autonomous uplink retransmissions ofa TB with one or more configured grants. The base station may determinea scheduling policy or a scheduling decision for the TB based on theinformation.

In an embodiment of the disclosure, the method may further comprise, atthe base station, receiving the user data from the terminal device.

In an embodiment of the disclosure, the method may further comprise, atthe base station, initiating a transmission of the received user data tothe host computer.

According to a twelfth aspect of the disclosure, there is provided acommunication system including a host computer comprising acommunication interface configured to receive user data originating froma transmission from a terminal device to a base station. The basestation may comprise a radio interface and processing circuitry. Thebase station's processing circuitry may be configured to receive, from aterminal device, information related to one or more autonomous uplinkretransmissions of a TB with one or more configured grants. The basestation's processing circuitry may be further configured to determine ascheduling policy or a scheduling decision for the TB based on theinformation.

In an embodiment of the disclosure, the communication system may furtherinclude the base station.

In an embodiment of the disclosure, the communication system may furtherinclude the terminal device. The terminal device may be configured tocommunicate with the base station.

In an embodiment of the disclosure, the processing circuitry of the hostcomputer may be configured to execute a host application. The terminaldevice may be configured to execute a client application associated withthe host application, thereby providing the user data to be received bythe host computer.

According to a thirteenth aspect of the disclosure, there is provided amethod implemented in a communication system including a network nodeand a terminal device. The method may comprise, at the terminal device,transmitting a TB to the network node with a first configured grant. Themethod may further comprise, at the terminal device, retransmitting theTB to the network node autonomously with a second configured grant. Themethod may further comprise, at the network node, receiving, from theterminal device, information related to one or more autonomous uplinkretransmissions of the TB with one or more configured grants. The methodmay further comprise, at the network node, determine a scheduling policyor a scheduling decision for the TB based on the information.

According to a fourteenth aspect of the disclosure, there is provided acommunication system comprising a terminal device and a network node.The terminal device may be configured to transmit a TB to the networknode with a first configured grant, and retransmit the TB to the networknode autonomously with a second configured grant. The network node maybe configured to receive, from the terminal device, information relatedto one or more autonomous uplink retransmissions of the TB with one ormore configured grants, and determine a scheduling policy or ascheduling decision for the TB based on the information.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other objects, features and advantages of the disclosure willbecome apparent from the following detailed description of illustrativeembodiments thereof, which are to be read in connection with theaccompanying drawings.

FIG. 1 is a flowchart illustrating a method implemented at a terminaldevice according to an embodiment of the disclosure;

FIG. 2 is a flowchart illustrating a method implemented at a terminaldevice according to another embodiment of the disclosure;

FIG. 3 is a flowchart illustrating a method implemented at a terminaldevice according to another embodiment of the disclosure;

FIG. 4 is a flowchart illustrating a method implemented at a terminaldevice according to another embodiment of the disclosure;

FIG. 5 is a flowchart illustrating a method implemented at a networknode according to an embodiment of the disclosure;

FIG. 6 is a block diagram showing an apparatus suitable for use inpracticing some embodiments of the disclosure;

FIG. 7 is a block diagram showing a terminal device according to anembodiment of the disclosure;

FIG. 8 is a block diagram showing a network node according to anembodiment of the disclosure;

FIG. 9 is a diagram showing a telecommunication network connected via anintermediate network to a host computer in accordance with someembodiments;

FIG. 10 is a diagram showing a host computer communicating via a basestation with a user equipment in accordance with some embodiments;

FIG. 11 is a flowchart illustrating a method implemented in acommunication system in accordance with some embodiments;

FIG. 12 is a flowchart illustrating a method implemented in acommunication system in accordance with some embodiments;

FIG. 13 is a flowchart illustrating a method implemented in acommunication system in accordance with some embodiments; and

FIG. 14 is a flowchart illustrating a method implemented in acommunication system in accordance with some embodiments.

DETAILED DESCRIPTION

For the purpose of explanation, details are set forth in the followingdescription in order to provide a thorough understanding of theembodiments disclosed. It is apparent, however, to those skilled in theart that the embodiments may be implemented without these specificdetails or with an equivalent arrangement.

In NR-U, both configured scheduling and dynamic scheduling will be used.Configured scheduling is used to allocate semi-static periodicassignments or grants for a UE. For uplink, there are two types ofconfigured scheduling schemes: Type 1 and Type 2. For Type 1, configuredgrants are configured via radio resource control (RRC) signaling only.For Type 2, similar configuration procedure as semi-persistentscheduling (SPS) uplink (UL) in long term evolution (LTE) was defined,i.e. some parameters are preconfigured via RRC signaling and somephysical layer parameters are configured via media access control (MAC)scheduling procedure. The detailed procedures can be found in 3GPPtechnical specification (TS) 38.321 V15.4.0. The configured uplinkscheduling will be also used in NR unlicensed operation. For NR-U, theconfigured scheduling can improve the channel access probability forphysical uplink shared channel (PUSCH) transmission because additionalLBT for physical downlink control channel (PDCCH) transmission per ULgrant is avoided and the UE can acquire channel for PUSCH transmissionusing a configured grant after LBT success. In this uplink transmissionprocedure, only single LBT procedure is needed compared to 3 LBTprocedures (one for scheduling request (SR) transmission (TX), one forPDCCH for UL grant and one for PUSCH TX) relying on SR/buffer statusreport (BSR) procedure. This can significantly improve the channelaccess probability for PUSCH transmission.

As captured in the 3GPP technical report (TR) 38.889 V16.0.0, allowingconsecutive configured grant resources in time without any gaps inbetween the resources and non-consecutive configured grant resources(not necessarily periodic) with gaps in between the resources isbeneficial and should be considered for NR in unlicensed spectrum.

For NR-U, certain enhancements of configured scheduling are needed. Forinstance, when the initial transmission using a configured grant isdetermined to be failed by a UE, the UE can perform automaticretransmission using another configured grant. Such enhancementconfigured scheduling scheme is referred to as autonomous uplink (AUL)transmission.

To support autonomous retransmission in uplink using a configured grant,a new timer was introduced to protect the HARQ procedure so that theretransmission can use the same HARQ process for retransmission as forthe initial transmission. The new timer (“CG retransmission timer”) isintroduced for auto retransmission (i.e. timer expiry=HARQ NACK) onconfigured grant for the case of the TB previously being transmitted ona configured grant. The new timer is started when the TB is actuallytransmitted on the configured grant and stopped upon reception of HARQfeedback (e.g. dynamic feedback indicator (DFI)) or dynamic grant forthe HARQ process. The legacy configured grant timer and behavior is keptfor preventing the configured grant overriding the TB scheduled bydynamic grant, i.e. it is (re)started upon reception of the PDCCH aswell as transmission on the PUSCH of dynamic grant.

With these agreements, a CG retransmission timer is started for a HARQprocess configured with autonomous uplink (AUL) transmission upon thedata transmission using a configured grant, and autonomousretransmission using another configured grant is triggered when the CGretransmission timer expires.

However, AUL is designed on top of the existing configured grantframework in NR Release 15, where the HARQ retransmission is fullycontrolled or scheduled by a next generation node B (gNB). In otherwords, the gNB determines when to complete transmission for a HARQprocess via providing a new grant to the HARQ process. AUL hasintroduced a new function to support autonomous HARQ retransmission uponexpiry of the CG retransmission timer. In this situation, there may beseveral issues below.

First, the gNB may not know how many transmission attempts that the UEhas performed so that the HARQ acknowledgement/non-acknowledgement (A/N)in the DFI may be not replied by the gNB in time, so that additionallatency for HARQ transmission may be caused.

Second, the UE may just continuously initiate autonomous HARQretransmissions for a HARQ process for a very long time. However, thegNB may not successfully receive the TB either due to bad radio channelquality or because the channel is seldom obtained due to LBT failures.

As a result, a huge delay may be incurred for a HARQ process configuredwith AUL. This may further block the transmission window at upper layerssuch as radio link control (RLC) layer, packet data convergence protocol(PDCP) layer or transmission control protocol (TCP) layer.

The present disclosure proposes an improved solution for uplinktransmission. The solution may be applied to a wireless communicationsystem including a terminal device and a network node such as a basestation or any other node with similar functionality. The terminaldevice can communicate through a radio access communication link withthe base station. The base station can provide radio accesscommunication links to terminal devices that are within itscommunication service cell. Note that the communications may beperformed between the terminal device and the base station according toany suitable communication standards and protocols. The terminal devicemay also be referred to as, for example, device, access terminal, userequipment (UE), mobile station, mobile unit, subscriber station, or thelike. It may refer to any end device that can access a wirelesscommunication network and receive services therefrom. By way of exampleand not limitation, the terminal device may include a portable computer,an image capture terminal device such as a digital camera, a gamingterminal device, a music storage and playback appliance, a mobile phone,a cellular phone, a smart phone, a tablet, a wearable device, a personaldigital assistant (PDA), or the like.

In an Internet of things (IoT) scenario, a terminal device may representa machine or other device that performs monitoring and/or measurements,and transmits the results of such monitoring and/or measurements toanother terminal device and/or a network equipment. In this case, theterminal device may be a machine-to-machine (M2M) device, which may, ina 3GPP context, be referred to as a machine-type communication (MTC)device. Particular examples of such machines or devices may includesensors, metering devices such as power meters, industrial machineries,bikes, vehicles, or home or personal appliances, e.g. refrigerators,televisions, personal wearables such as watches, and so on.

Now, several embodiments will be described to explain the improvedsolution for uplink transmission. Although these embodiments will bedescribed in the context of NR-U, the principle of the disclosure isalso applicable to other unlicensed operation scenarios (e.g. LTELAA/eLAA/feLAA/MuLteFire) and licensed operation scenarios whereautonomous uplink retransmission using configured grant may be adopted.The term LAA refers to licensed assisted access, the term eLAA refers toenhanced LAA and the term feLAA refers to further enhanced LAA.

As a first embodiment, for a HARQ process configured with AUL using aconfigured grant, a maximum time period may be configured during which aUE is allowed to perform autonomous retransmissions. In other words, theUE stops to retransmit a TB for the corresponding HARQ process when theconfigured maximum time period has elapsed. In this way, the autonomousretransmission is only allowed within the delay budget. For example, themaximum time period may be configured according to the latencyrequirement of the associated service data or logical channels (LCHs).

For example, a corresponding timer may be defined for this purpose. Thetimer may be started when for example any of below events occurs: afirst event that the MAC PDU has been built and the MAC PDU is deliveredto the HARQ process; a second event that the first LBT operation isstarted for the first transmission attempt of the TB; and a third eventthat the first OFDM symbol of the first potential transmissionopportunity for the TB appears.

The timer may be stopped when the UE has received a HARQ ACK for thecorresponding HARQ process. Upon expiration of the timer withoutreceiving HARQ ACK, a HARQ failure for the HARQ process may be triggeredand reported to upper layers above the MAC layer. Optionally, the reportmessage may also comprise other information, such as the number oftransmission attempts that the UE has tried, HARQ process identifier(ID), etc. Upon this, the UE MAC may inform the upper layer (such asRLC) to trigger retransmission for corresponding PDUs. Optionally, theUE may also send a HARQ failure report to the gNB via signaling meanssuch as RRC, MAC CE or Layer 1/Layer 2 (L1/L2) control signaling.

In this embodiment, the time length may contain the time for the LBToperations (such as the time when LBT failures occur). The timer may bea newly defined timer, or an existing timer (such asconfiguredGrantTimer) may be reused as the timer. In caseconfiguredGrantTimer is reused for controlling maximum AULretransmissions attempts, upon expiration of the configuredGrantTimer,the UE may further check additional information to know the reason whythe timer is expired. For example, if the timer was notstarted/restarted due to a transmission with a configured grant for thisHARQ process, the UE assumes HARQ ACK for the associated HARQ processupon the expiration of the timer. Otherwise, the UE assumes HARQ failurefor the associated HARQ process upon the expiration of the timer. Forexample, the term “start” may mean the timer is started for the firsttime or started after the timer expires. The term “restart” may mean thetimer is started again before the timer expires.

In case configuredGrantTimer is not reused, the UE may be configured notto start the configuredGrantTimer upon a new transmission for theassociated HARQ process with a configured grant. Instead, the new timeris started.

As a second embodiment, for a HARQ process configured with AUL using aconfigured grant, a maximum number of HARQ transmission attempts may beconfigured. Similar to the first embodiment, the maximum number of HARQtransmission attempts may be configured according to the latencyrequirement of the associated service data or LCHs. When the maximumHARQ transmission attempts are reached, while the UE has not receivedHARQ ACK, a HARQ failure for the HARQ process may be triggered andreported to upper layers above the MAC layer. Optionally, the reportmessage may comprise other information, such as the number oftransmission attempts that the UE has tried, HARQ process ID, etc. Uponthis, the UE MAC may inform the upper layer (such as RLC) to triggerretransmission for corresponding PDUs. Optionally, the UE may send aHARQ failure report to the gNB via signaling means such as RRC, MAC CEor L1/L2 control signaling. In this embodiment, the missed transmissionattempts due to LBT failures may be considered.

As a third embodiment, a UE may indicate the number of transmissionattempts or the experienced delay for a TB explicitly or implicitly. Asan example, the information may be included in the uplink controlinformation (UCI) associated with the PUSCH transmission using aconfigured grant. The UCI may be carried on PUCCH, or on PUSCH (may bemultiplexed with the data same as PUCCH-UCI transmitted on PUSCH). Asanother example, the information may be included in an RRC signaling, anMAC CE or an L1/L2 signaling. As yet another example, the number oftransmission attempts may be implicitly indicated via redundant version(RVI) of the TB, which may be included in the UCI.

Upon reception of the information via such as UCI, the gNB may determinethe experienced delay for the corresponding TB. Thereafter, the gNB maydetermine a proper scheduling policy for the corresponding TB (such asscheduling priority, parameters for PDCCH to convey UL grant for theretransmission, PUSCH duration length (e.g. subcarrier spacing, numberof OFDM symbols), transmit power parameters, and PUSCH preparationdelay, etc).

As an exemplary example, in order to meet a given delay threshold forthe TB, the gNB may take at least one of below actions to ensure the UEto finish transmissions of the associated HARQ process within a maximumtime period, which may be configured by the gNB:

-   -   1) give higher scheduling priority for the TB;    -   2) transmit DCI using a more reliable PDCCH format (e.g. high        aggregation level) for UL grant transmission;    -   3) schedule resource for the TB with high PUSCH transmission        power and short PUSCH preparation (such as K2)/transmission        duration.        In this way, the autonomous uplink HARQ retransmission        performance can be enhanced and meanwhile the latency        requirement can be ensured.

Alternatively, upon reception of the information from the UE, the gNBmay decide to terminate the transmissions of the associated HARQprocess, for example, if the gNB thinks that the UE has used too manyresources. The gNB may then reschedule the resources to other data. Thetermination of transmissions may be signaled via any of signaling meansincluding, but not limited to, a L1/L2 signaling such as DCI indication;a MAC CE; and an RRC signaling. Upon reception of the terminationsignaling for a HARQ process, the UE MAC may inform the upper layer ofthis and may further trigger upper layer retransmissions.

As a fourth embodiment, for a pending TB associated with a HARQ process,after a predetermined number of transmission attempts or a configuredtime period while the UE has not received any HARQ A/N for the TB fromthe gNB, the UE may transmit the TB using another HARQ process. In thiscase, the timer for the maximum time period associated with the new HARQprocess may be started, while the old timer may be stopped.

The UE may also use a dynamic grant to retransmit the TB with the sameor a different HARQ process and the timer may be also restarted. Thepending TB may be treated as a separate new transmission by the UE forsubsequent transmission attempts.

As a fifth embodiment, when the timer is going to expire or the maximumnumber of transmission attempts is going to be reached, the UE mayperform proactive retransmissions for the corresponding TB withoutwaiting for DFI feedback or the expiration of the CG retransmissiontimer. In this way, the data transmission reliability can be improvedwhen the latency budget is to be exhausted.

As a sixth embodiment, the timer may be stopped when the UE has receiveda dynamic grant for retransmissions of the TB for the corresponding HARQprocess. In this case, the gNB takes over scheduling for this HARQprocess.

As a seventh embodiment, the UE MAC may use transmissionopportunities/occasions provided by a different configured grantconfiguration to transmit a pending TB which has been built according toa configured grant belonging to another configured grant configuration.In this way, more transmission opportunities/occasions are achievablefor the pending TB. The related description of the configured grantconfiguration can be found from clause 6.3.2 (ConfiguredGrantConfigInformation element) of 3GPP TS 38.331 (RRC protocol) V15.5.1. Asdefined in this technical specification, the configured grantconfiguration can be signaled by the network to a terminal device.

Hereinafter, the solution will be further described with reference toFIGS. 1-14. FIG. 1 is a flowchart illustrating a method implemented at aterminal device according to an embodiment of the disclosure. At block102, the terminal device transmits a TB to a network node with a firstconfigured grant. The network node may be a base station or any othernode with similar functionality. The TB may be transmitted with a HARQprocess. At block 104, the terminal device retransmits the TB to thenetwork node autonomously with a second configured grant. The TB may beretransmitted autonomously with the second configured grant when theterminal device determines that an autonomous retransmission with thesecond configured grant is allowed.

To restrict the delay caused by the autonomous uplink retransmissions,there may be five options. As the first option, the autonomousretransmission of the TB stops when a predetermined maximum time periodhas elapsed. The predetermined maximum time period may be based on alatency requirement of related service data or related one or morelogical channels. Optionally, the predetermined maximum time period maycontain time elapsed for one or more LBT operations.

For example, a timer whose timer value equals the predetermined maximumtime period may be used such that the autonomous retransmission of theTB stops when the timer expires. The timer may be started at a timepoint related to the transmission of the TB. As an exemplary example,the timer may be started when one of following events occurs: a firstevent that a MAC PDU corresponding to the TB has been generated; asecond event that the first LBT operation is started for the firsttransmission attempt of the TB; and a third event that the firstpotential transmission opportunity for the TB occurs. The timer may bestopped when the terminal device receives an acknowledgement for the TBor a dynamic grant for retransmission of the TB. The timer may be anewly introduced timer. Alternatively, a configured grant timer may bereused as the timer.

As the second option, the autonomous retransmission of the TB stops whena predetermined maximum number of transmission attempts is reached. Forexample, the predetermined maximum number of transmission attempts maybe based on a latency requirement of related service data or related oneor more logical channels. The transmission attempts may contain theinitial transmission and subsequent retransmissions. Additionally, thetransmission attempts may further contain the missed attempts (for theinitial transmission and subsequent retransmissions) due to LBTfailures.

In the above first and second options, when the terminal device has notreceived an acknowledgement for the TB after the predetermined maximumtime period has elapsed or the predetermined maximum number oftransmission attempts is reached, the terminal device may optionallytransmit a failure report for the TB to the network node at block 206 asshown in FIG. 2. Alternatively, the terminal device may trigger upperlayer retransmissions of the data corresponding to the TB. The upperlayer refers to the layer above MAC layer.

Optionally, when the predetermined maximum time period is to elapse orthe predetermined maximum number of transmission attempts is to bereached, the autonomous retransmission of the TB may be performedproactively. For example, the autonomous retransmission of the TB may beperformed without waiting a feedback for the TB or without waiting anexpiration of a configured grant retransmission timer. The expiration ofthe configured grant retransmission timer may be used to trigger anautonomous retransmission using a configured grant.

As the third option, the terminal device indicates, to the network node,a number of transmission attempts for the TB or delay experienced forthe transmissions of the TB at block 308 as shown in FIG. 3. Forexample, the number of the transmission attempts or the experienceddelay may be indicated by one or more of: redundant version of the TB;UCI; RRC signaling; MAC CE; and L1/L2 signaling. In this way, thenetwork node may use the indicated information to improve theretransmissions from the terminal device, such that the retransmissionscan be completed within a predetermined maximum time period.Alternatively, the network node may make a scheduling decision toterminate the retransmissions for the TB. Correspondingly, the terminaldevice may receive a signaling indicating termination of retransmissionsfor the TB at block 310. In response to the signaling, the terminaldevice may trigger upper layer retransmissions of the data correspondingto the TB at block 312.

As the fourth option, the autonomous retransmission of the TB isperformed multiple times. A first part of the multiple autonomousretransmissions is performed with the same HARQ process and a secondpart of the multiple autonomous retransmissions is performed withanother HARQ process. The first part or second part may be one or moreof the multiple autonomous retransmissions. For example, the anotherHARQ process may be used when the terminal device has not received anyHARQ feedback for the TB after a predetermined number of transmissionattempts or a predetermined time period. The fourth option may be usedin combination with any of the above first to third options.Alternatively, in any of the above first to third options, theautonomous retransmission of the TB may be performed one or more timeswith the same HARQ process.

As described above, the UE MAC may use transmissionopportunities/occasions provided by a different configured grantconfiguration to transmit a pending TB which has been built according toa configured grant belonging to another configured grant configuration.Thus, as the fifth option, the second configured grant belongs to afirst configured grant configuration. The terminal device retransmitsthe TB to the network node autonomously with a third configured grantbelonging to the first configured grant configuration or a secondconfigured grant configuration, or with the second and third configuredgrants, at block 414 as shown in FIG. 4. In this case, it is possiblethat the first configured grant belongs to the first or secondconfigured grant configuration. It is also possible that the firstconfigured grant belongs to a third configured grant configuration.Accordingly, the size of the TB may be determined based on the first,second or third configured grant configuration. Note that the first,second or third configured grant configuration may be received from thenetwork node, as mentioned above. Also note that any one of the abovefirst to fifth options may be used alone or in combination.

FIG. 5 is a flowchart illustrating a method implemented at a networknode according to an embodiment of the disclosure. The network node maybe a base station or any other node with similar functionality. At block502, the base station receives, from a terminal device, informationrelated to one or more autonomous uplink retransmissions of a TB withone or more configured grants. For example, the information may compriseone or more of: the number of transmission attempts for the TB or delayexperienced for the transmissions of the TB; a HARQ process identifierfor the TB; and a failure indication that the TB is not to beretransmitted autonomously from the terminal device.

At block 504, the network node determines a scheduling policy or ascheduling decision for the TB based on the information. The schedulingpolicy may be determined to ensure the retransmissions from the terminaldevice to be completed within a predetermined maximum time period. Forexample, the scheduling policy may comprise one or more of: schedulingpriority for the TB (e.g. a higher scheduling priority may bedetermined); parameters for PDCCH carrying an uplink grant forretransmission of the TB (e.g. a more reliable PDCCH format may bedetermined); PUSCH duration length for the TB (e.g. a short PUSCHduration length may be determined); transmission power parameters forthe TB (e.g. a high transmission power may be determined); and PUSCHpreparation delay for the TB (e.g. a short PUSCH preparation delay maybe determined).

The scheduling decision may indicate termination of retransmissions forthe TB. For example, if the terminal device has used too many resources,the network node may make this scheduling decision. A signalingindicating the scheduling decision may be sent to the terminal device atblock 506. The signaling may be sent as one or more of: a L1/L2signaling; a MAC CE; and an RRC signaling.

Blocks 502˜506 correspond to the third option described above.Alternatively or additionally, the network node may transmit, to aterminal device, information indicating a predetermined maximum numberof transmission attempts or a predetermined maximum time period at block501, which corresponds to the above first and second options. Theautonomous retransmission of a TB stops when the predetermined maximumnumber of transmission attempts is reached or the predetermined maximumtime period has elapsed. In addition, as mentioned above, the configuredgrant configuration can be signaled by the network to a terminal device.Thus, the above method implemented at the network node may furthercomprise transmitting one or more configured grant configurations to theterminal device. It should be also noted that two blocks shown insuccession in the figures may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved.

Based on the above description, at least one aspect of the disclosureprovides a method implemented in a communication system including anetwork node and a terminal device. The method may comprise, at theterminal device, transmitting a TB to the network node with a firstconfigured grant. The method may further comprise, at the terminaldevice, retransmitting the TB to the network node autonomously with asecond configured grant. The method may further comprise, at the networknode, receiving, from the terminal device, information related to one ormore autonomous uplink retransmissions of the TB with one or moreconfigured grants. The method may further comprise, at the network node,determining a scheduling policy or a scheduling decision for the TBbased on the information.

FIG. 6 is a block diagram showing an apparatus suitable for use inpracticing some embodiments of the disclosure. For example, any one ofthe terminal device and the network node described above may beimplemented through the apparatus 600. As shown, the apparatus 600 mayinclude a processor 610, a memory 620 that stores a program, andoptionally a communication interface 630 for communicating data withother external devices through wired and/or wireless communication.

The program includes program instructions that, when executed by theprocessor 610, enable the apparatus 600 to operate in accordance withthe embodiments of the present disclosure, as discussed above. That is,the embodiments of the present disclosure may be implemented at least inpart by computer software executable by the processor 610, or byhardware, or by a combination of software and hardware.

The memory 620 may be of any type suitable to the local technicalenvironment and may be implemented using any suitable data storagetechnology, such as semiconductor based memory devices, flash memories,magnetic memory devices and systems, optical memory devices and systems,fixed memories and removable memories. The processor 610 may be of anytype suitable to the local technical environment, and may include one ormore of general purpose computers, special purpose computers,microprocessors, digital signal processors (DSPs) and processors basedon multi-core processor architectures, as non-limiting examples.

FIG. 7 is a block diagram showing a terminal device according to anembodiment of the disclosure. As shown, the terminal device 700comprises a transmission module 702 and a retransmission module 704. Thetransmission module 702 may be configured to transmit a TB to a networknode with a first configured grant, as described above with respect toblock 102. The retransmission module 704 may be configured to retransmitthe TB to the network node autonomously with a second configured grant,as described above with respect to block 104.

FIG. 8 is a block diagram showing a network node according to anembodiment of the disclosure. As shown, the network node 800 comprises areception module 802 and a determination module 804. The receptionmodule 802 may be configured to receive, from a terminal device,information related to one or more autonomous uplink retransmissions ofa TB with one or more configured grants, as described above with respectto block 502. The determination module 804 may be configured todetermining a scheduling policy or a scheduling decision for the TBbased on the information, as described above with respect to block 504.The modules described above may be implemented by hardware, or software,or a combination of both.

Based on the above description, at least one aspect of the disclosureprovides a communication system comprising a terminal device and anetwork node. The terminal device may be configured to transmit a TB tothe network node with a first configured grant, and retransmit the TB tothe network node autonomously with a second configured grant. Thenetwork node may be configured to receive, from the terminal device,information related to one or more autonomous uplink retransmissions ofthe TB with one or more configured grants, and determine a schedulingpolicy or a scheduling decision for the TB based on the information.

With reference to FIG. 9, in accordance with an embodiment, acommunication system includes telecommunication network 3210, such as a3 GPP-type cellular network, which comprises access network 3211, suchas a radio access network, and core network 3214. Access network 3211comprises a plurality of base stations 3212 a, 3212 b, 3212 c, such asNBs, eNBs, gNBs or other types of wireless access points, each defininga corresponding coverage area 3213 a, 3213 b, 3213 c. Each base station3212 a, 3212 b, 3212 c is connectable to core network 3214 over a wiredor wireless connection 3215. A first UE 3291 located in coverage area3213 c is configured to wirelessly connect to, or be paged by, thecorresponding base station 3212 c. A second UE 3292 in coverage area3213 a is wirelessly connectable to the corresponding base station 3212a. While a plurality of UEs 3291, 3292 are illustrated in this example,the disclosed embodiments are equally applicable to a situation where asole UE is in the coverage area or where a sole UE is connecting to thecorresponding base station 3212.

Telecommunication network 3210 is itself connected to host computer3230, which may be embodied in the hardware and/or software of astandalone server, a cloud-implemented server, a distributed server oras processing resources in a server farm. Host computer 3230 may beunder the ownership or control of a service provider, or may be operatedby the service provider or on behalf of the service provider.Connections 3221 and 3222 between telecommunication network 3210 andhost computer 3230 may extend directly from core network 3214 to hostcomputer 3230 or may go via an optional intermediate network 3220.Intermediate network 3220 may be one of, or a combination of more thanone of, a public, private or hosted network; intermediate network 3220,if any, may be a backbone network or the Internet; in particular,intermediate network 3220 may comprise two or more sub-networks (notshown).

The communication system of FIG. 9 as a whole enables connectivitybetween the connected UEs 3291, 3292 and host computer 3230. Theconnectivity may be described as an over-the-top (OTT) connection 3250.Host computer 3230 and the connected UEs 3291, 3292 are configured tocommunicate data and/or signaling via OTT connection 3250, using accessnetwork 3211, core network 3214, any intermediate network 3220 andpossible further infrastructure (not shown) as intermediaries. OTTconnection 3250 may be transparent in the sense that the participatingcommunication devices through which OTT connection 3250 passes areunaware of routing of uplink and downlink communications. For example,base station 3212 may not or need not be informed about the past routingof an incoming downlink communication with data originating from hostcomputer 3230 to be forwarded (e.g., handed over) to a connected UE3291. Similarly, base station 3212 need not be aware of the futurerouting of an outgoing uplink communication originating from the UE 3291towards the host computer 3230.

Example implementations, in accordance with an embodiment, of the UE,base station and host computer discussed in the preceding paragraphswill now be described with reference to FIG. 10. In communication system3300, host computer 3310 comprises hardware 3315 including communicationinterface 3316 configured to set up and maintain a wired or wirelessconnection with an interface of a different communication device ofcommunication system 3300. Host computer 3310 further comprisesprocessing circuitry 3318, which may have storage and/or processingcapabilities. In particular, processing circuitry 3318 may comprise oneor more programmable processors, application-specific integratedcircuits, field programmable gate arrays or combinations of these (notshown) adapted to execute instructions. Host computer 3310 furthercomprises software 3311, which is stored in or accessible by hostcomputer 3310 and executable by processing circuitry 3318. Software 3311includes host application 3312. Host application 3312 may be operable toprovide a service to a remote user, such as UE 3330 connecting via OTTconnection 3350 terminating at UE 3330 and host computer 3310. Inproviding the service to the remote user, host application 3312 mayprovide user data which is transmitted using OTT connection 3350.

Communication system 3300 further includes base station 3320 provided ina telecommunication system and comprising hardware 3325 enabling it tocommunicate with host computer 3310 and with UE 3330. Hardware 3325 mayinclude communication interface 3326 for setting up and maintaining awired or wireless connection with an interface of a differentcommunication device of communication system 3300, as well as radiointerface 3327 for setting up and maintaining at least wirelessconnection 3370 with UE 3330 located in a coverage area (not shown inFIG. 10) served by base station 3320. Communication interface 3326 maybe configured to facilitate connection 3360 to host computer 3310.Connection 3360 may be direct or it may pass through a core network (notshown in FIG. 10) of the telecommunication system and/or through one ormore intermediate networks outside the telecommunication system. In theembodiment shown, hardware 3325 of base station 3320 further includesprocessing circuitry 3328, which may comprise one or more programmableprocessors, application-specific integrated circuits, field programmablegate arrays or combinations of these (not shown) adapted to executeinstructions. Base station 3320 further has software 3321 storedinternally or accessible via an external connection.

Communication system 3300 further includes UE 3330 already referred to.Its hardware 3335 may include radio interface 3337 configured to set upand maintain wireless connection 3370 with a base station serving acoverage area in which UE 3330 is currently located. Hardware 3335 of UE3330 further includes processing circuitry 3338, which may comprise oneor more programmable processors, application-specific integratedcircuits, field programmable gate arrays or combinations of these (notshown) adapted to execute instructions. UE 3330 further comprisessoftware 3331, which is stored in or accessible by UE 3330 andexecutable by processing circuitry 3338. Software 3331 includes clientapplication 3332. Client application 3332 may be operable to provide aservice to a human or non-human user via UE 3330, with the support ofhost computer 3310. In host computer 3310, an executing host application3312 may communicate with the executing client application 3332 via OTTconnection 3350 terminating at UE 3330 and host computer 3310. Inproviding the service to the user, client application 3332 may receiverequest data from host application 3312 and provide user data inresponse to the request data. OTT connection 3350 may transfer both therequest data and the user data. Client application 3332 may interactwith the user to generate the user data that it provides.

It is noted that host computer 3310, base station 3320 and UE 3330illustrated in FIG. 10 may be similar or identical to host computer3230, one of base stations 3212 a, 3212 b, 3212 c and one of UEs 3291,3292 of FIG. 9, respectively. This is to say, the inner workings ofthese entities may be as shown in FIG. 10 and independently, thesurrounding network topology may be that of FIG. 9.

In FIG. 10, OTT connection 3350 has been drawn abstractly to illustratethe communication between host computer 3310 and UE 3330 via basestation 3320, without explicit reference to any intermediary devices andthe precise routing of messages via these devices. Networkinfrastructure may determine the routing, which it may be configured tohide from UE 3330 or from the service provider operating host computer3310, or both. While OTT connection 3350 is active, the networkinfrastructure may further take decisions by which it dynamicallychanges the routing (e.g., on the basis of load balancing considerationor reconfiguration of the network).

Wireless connection 3370 between UE 3330 and base station 3320 is inaccordance with the teachings of the embodiments described throughoutthis disclosure. One or more of the various embodiments improve theperformance of OTT services provided to UE 3330 using OTT connection3350, in which wireless connection 3370 forms the last segment. Moreprecisely, the teachings of these embodiments may improve the latencyand thereby provide benefits such as reduced user waiting time.

A measurement procedure may be provided for the purpose of monitoringdata rate, latency and other factors on which the one or moreembodiments improve. There may further be an optional networkfunctionality for reconfiguring OTT connection 3350 between hostcomputer 3310 and UE 3330, in response to variations in the measurementresults. The measurement procedure and/or the network functionality forreconfiguring OTT connection 3350 may be implemented in software 3311and hardware 3315 of host computer 3310 or in software 3331 and hardware3335 of UE 3330, or both. In embodiments, sensors (not shown) may bedeployed in or in association with communication devices through whichOTT connection 3350 passes; the sensors may participate in themeasurement procedure by supplying values of the monitored quantitiesexemplified above, or supplying values of other physical quantities fromwhich software 3311, 3331 may compute or estimate the monitoredquantities. The reconfiguring of OTT connection 3350 may include messageformat, retransmission settings, preferred routing etc.; thereconfiguring need not affect base station 3320, and it may be unknownor imperceptible to base station 3320. Such procedures andfunctionalities may be known and practiced in the art. In certainembodiments, measurements may involve proprietary UE signalingfacilitating host computer 3310's measurements of throughput,propagation times, latency and the like. The measurements may beimplemented in that software 3311 and 3331 causes messages to betransmitted, in particular empty or ‘dummy’ messages, using OTTconnection 3350 while it monitors propagation times, errors etc.

FIG. 11 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 9 and 10. Forsimplicity of the present disclosure, only drawing references to FIG. 11will be included in this section. In step 3410, the host computerprovides user data. In substep 3411 (which may be optional) of step3410, the host computer provides the user data by executing a hostapplication. In step 3420, the host computer initiates a transmissioncarrying the user data to the UE. In step 3430 (which may be optional),the base station transmits to the UE the user data which was carried inthe transmission that the host computer initiated, in accordance withthe teachings of the embodiments described throughout this disclosure.In step 3440 (which may also be optional), the UE executes a clientapplication associated with the host application executed by the hostcomputer.

FIG. 12 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 9 and 10. Forsimplicity of the present disclosure, only drawing references to FIG. 12will be included in this section. In step 3510 of the method, the hostcomputer provides user data. In an optional substep (not shown) the hostcomputer provides the user data by executing a host application. In step3520, the host computer initiates a transmission carrying the user datato the UE. The transmission may pass via the base station, in accordancewith the teachings of the embodiments described throughout thisdisclosure. In step 3530 (which may be optional), the UE receives theuser data carried in the transmission.

FIG. 13 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 9 and 10. Forsimplicity of the present disclosure, only drawing references to FIG. 13will be included in this section. In step 3610 (which may be optional),the UE receives input data provided by the host computer. Additionallyor alternatively, in step 3620, the UE provides user data. In substep3621 (which may be optional) of step 3620, the UE provides the user databy executing a client application. In substep 3611 (which may beoptional) of step 3610, the UE executes a client application whichprovides the user data in reaction to the received input data providedby the host computer. In providing the user data, the executed clientapplication may further consider user input received from the user.Regardless of the specific manner in which the user data was provided,the UE initiates, in substep 3630 (which may be optional), transmissionof the user data to the host computer. In step 3640 of the method, thehost computer receives the user data transmitted from the UE, inaccordance with the teachings of the embodiments described throughoutthis disclosure.

FIG. 14 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 9 and 10. Forsimplicity of the present disclosure, only drawing references to FIG. 14will be included in this section. In step 3710 (which may be optional),in accordance with the teachings of the embodiments described throughoutthis disclosure, the base station receives user data from the UE. Instep 3720 (which may be optional), the base station initiatestransmission of the received user data to the host computer. In step3730 (which may be optional), the host computer receives the user datacarried in the transmission initiated by the base station.

In general, the various exemplary embodiments may be implemented inhardware or special purpose circuits, software, logic or any combinationthereof. For example, some aspects may be implemented in hardware, whileother aspects may be implemented in firmware or software which may beexecuted by a controller, microprocessor or other computing device,although the disclosure is not limited thereto. While various aspects ofthe exemplary embodiments of this disclosure may be illustrated anddescribed as block diagrams, flow charts, or using some other pictorialrepresentation, it is well understood that these blocks, apparatus,systems, techniques or methods described herein may be implemented in,as non-limiting examples, hardware, software, firmware, special purposecircuits or logic, general purpose hardware or controller or othercomputing devices, or some combination thereof.

As such, it should be appreciated that at least some aspects of theexemplary embodiments of the disclosure may be practiced in variouscomponents such as integrated circuit chips and modules. It should thusbe appreciated that the exemplary embodiments of this disclosure may berealized in an apparatus that is embodied as an integrated circuit,where the integrated circuit may comprise circuitry (as well as possiblyfirmware) for embodying at least one or more of a data processor, adigital signal processor, baseband circuitry and radio frequencycircuitry that are configurable so as to operate in accordance with theexemplary embodiments of this disclosure.

It should be appreciated that at least some aspects of the exemplaryembodiments of the disclosure may be embodied in computer-executableinstructions, such as in one or more program modules, executed by one ormore computers or other devices. Generally, program modules includeroutines, programs, objects, components, data structures, etc. thatperform particular tasks or implement particular abstract data typeswhen executed by a processor in a computer or other device. The computerexecutable instructions may be stored on a computer readable medium suchas a hard disk, optical disk, removable storage media, solid statememory, RAM, etc. As will be appreciated by one skilled in the art, thefunction of the program modules may be combined or distributed asdesired in various embodiments. In addition, the function may beembodied in whole or in part in firmware or hardware equivalents such asintegrated circuits, field programmable gate arrays (FPGA), and thelike.

References in the present disclosure to “one embodiment”, “anembodiment” and so on, indicate that the embodiment described mayinclude a particular feature, structure, or characteristic, but it isnot necessary that every embodiment includes the particular feature,structure, or characteristic. Moreover, such phrases are not necessarilyreferring to the same embodiment. Further, when a particular feature,structure, or characteristic is described in connection with anembodiment, it is submitted that it is within the knowledge of oneskilled in the art to implement such feature, structure, orcharacteristic in connection with other embodiments whether or notexplicitly described.

It should be understood that, although the terms “first”, “second” andso on may be used herein to describe various elements, these elementsshould not be limited by these terms. These terms are only used todistinguish one element from another. For example, a first element couldbe termed a second element, and similarly, a second element could betermed a first element, without departing from the scope of thedisclosure. As used herein, the term “and/or” includes any and allcombinations of one or more of the associated listed terms.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to limit the present disclosure. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”,“comprising”, “has”, “having”, “includes” and/or “including”, when usedherein, specify the presence of stated features, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, elements, components and/or combinations thereof. Theterms “connect”, “connects”, “connecting” and/or “connected” used hereincover the direct and/or indirect connection between two elements.

The present disclosure includes any novel feature or combination offeatures disclosed herein either explicitly or any generalizationthereof. Various modifications and adaptations to the foregoingexemplary embodiments of this disclosure may become apparent to thoseskilled in the relevant arts in view of the foregoing description, whenread in conjunction with the accompanying drawings. However, any and allmodifications will still fall within the scope of the non-Limiting andexemplary embodiments of this disclosure.

What is claimed is:
 1. A method in a terminal device comprising:transmitting (102) a transport block, TB, to a network node with a firstconfigured grant; and retransmitting (104) the TB to the network nodeautonomously with a second configured grant.
 2. The method according toclaim 1, wherein the autonomous retransmission of the TB stops when atimer whose timer value equals a predetermined maximum time periodexpires.
 3. The method according to claim 1 or 2, wherein the secondconfigured grant belongs to a first configured grant configuration; andwherein the method further comprises: retransmitting (414) the TB to thenetwork node autonomously with a third configured grant belonging to asecond configured grant configuration.
 4. The method according to claim1 or 2, wherein the second configured grant belongs to a firstconfigured grant configuration; and wherein the method furthercomprises: retransmitting (414) the TB to the network node autonomouslywith a third configured grant belonging to the first configured grantconfiguration.
 5. The method according to claim 3 or 4, wherein thefirst configured grant belongs to the first or second configured grantconfiguration.
 6. The method according to claim 3 or 4, wherein thefirst configured grant belongs to a third configured grantconfiguration.
 7. The method according to any of claims 1 to 6, whereinthe TB is transmitted with a hybrid automatic repeat request, HARQ,process.
 8. The method according to any of claims 1 to 7, wherein theautonomous retransmission of the TB is performed one or more times withthe same HARQ process.
 9. The method according to any of claims 2 to 8,wherein the timer is started at a time point related to the transmissionof the TB.
 10. The method according to any of claims 2 to 9, wherein thetimer is stopped when the terminal device receives an acknowledgementfor the TB.
 11. The method according to any of claims 3 to 10, wherein asize of the TB is determined based on the first, second or thirdconfigured grant configuration.
 12. The method according to any ofclaims 3 to 11, wherein the first, second or third configured grantconfiguration is received from the network node.
 13. The methodaccording to any of claims 1 to 12, wherein the TB is retransmittedautonomously with the second configured grant when the terminal devicedetermines that an autonomous retransmission with the second configuredgrant is allowed.
 14. The method according to any of claims 7 to 13,wherein the autonomous retransmission of the TB is performed multipletimes; and wherein a first part of the multiple autonomousretransmissions is performed with the same HARQ process and a secondpart of the multiple autonomous retransmissions is performed withanother HARQ process.
 15. The method according to claim 14, wherein theanother HARQ process is used when the terminal device has not receivedany HARQ feedback for the TB after a predetermined number oftransmission attempts or a predetermined time period.
 16. The methodaccording to any of claims 1 to 15, wherein the second configured grantbelongs to a first configured grant configuration; and wherein themethod further comprises: retransmitting (414) the TB to the networknode autonomously with the second and third configured grants.
 17. Themethod according to any of claims 1 to 16, wherein the autonomousretransmission of the TB stops when a predetermined maximum number oftransmission attempts is reached or a predetermined maximum time periodhas elapsed.
 18. The method according to claim 17, wherein thepredetermined maximum number of transmission attempts or thepredetermined maximum time period is based on a latency requirement ofrelated service data or related one or more logical channels.
 19. Themethod according to claim 17 or 18, further comprising: when theterminal device has not received an acknowledgement for the TB after thepredetermined maximum number of transmission attempts is reached or thepredetermined maximum time period has elapsed, transmitting (206) afailure report for the TB to the network node.
 20. The method accordingto any of claims 17 to 19, wherein the transmission attempts contain oneor more transmission attempts missed due to listen before talk, LBT,failure; or wherein the predetermined maximum time period contain timeelapsed for one or more LBT operations.
 21. The method according to anyof claims 17 to 20, wherein when the predetermined maximum number oftransmission attempts is to be reached or the predetermined maximum timeperiod is to elapse, the autonomous retransmission of the TB isperformed proactively.
 22. The method according to claim 21, wherein theautonomous retransmission of the TB is performed proactively by:performing the autonomous retransmission of the TB without waiting afeedback for the TB or without waiting an expiration of a configuredgrant retransmission timer; and wherein the expiration of the configuredgrant retransmission timer is used to trigger an autonomousretransmission using a configured grant.
 23. The method according to anyof claims 2 to 22, wherein the timer is stopped when the terminal devicereceives a dynamic grant for retransmission of the TB.
 24. The methodaccording to claim 23, wherein the timer is started when one offollowing events occurs: a media access control, MAC, protocol dataunit, PDU, corresponding to the TB has been generated; a first LBToperation is started for a first transmission attempt of the TB; and afirst potential transmission opportunity for the TB occurs.
 25. Themethod according to any of claims 2 to 24, wherein a configured granttimer is reused as the timer.
 26. The method according to any of claims1 to 25, further comprising: indicating (308), to the network node, anumber of transmission attempts for the TB or delay experienced for thetransmissions of the TB.
 27. The method according to claim 26, whereinthe number of the transmission attempts or the experienced delay isindicated by one or more of: redundant version of the TB; uplink controlinformation, UCI; radio resource control, RRC, signaling; MAC controlelement, CE; and Layer 1 or Layer 2 signaling.
 28. The method accordingto claim 26 or 27, further comprising: receiving (310) a signalingindicating termination of retransmissions for the TB.
 29. The methodaccording to claim 28, further comprising: in response to the signaling,triggering (312) upper layer retransmissions of the data correspondingto the TB.
 30. A method in a network node comprising: receiving (502),from a terminal device, information related to one or more autonomousuplink retransmissions of a transport block, TB, with one or moreconfigured grants; and determining (504) a scheduling policy or ascheduling decision for the TB based on the information.
 31. The methodaccording to claim 30, further comprising: transmitting one or moreconfigured grant configurations to the terminal device.
 32. The methodaccording to claim 30 or 31, wherein the scheduling policy is determinedto ensure the retransmissions from the terminal device to be completedwithin a predetermined maximum time period.
 33. The method according toclaim 30 or 31, wherein the scheduling decision indicates termination ofretransmissions for the TB.
 34. The method according to any of claims 30to 33, further comprising: sending (506) a signaling indicating thescheduling decision to the terminal device.
 35. The method according toclaim 34, wherein the signaling is sent as one or more of: a Layer1/Layer 2 signaling; a MAC CE; and an RRC signaling.
 36. The methodaccording to any of claims 30 to 35, wherein the information comprisesone or more of: a number of transmission attempts for the TB or delayexperienced for the transmissions of the TB; a hybrid automatic repeatrequest, HARQ, process identifier for the TB; and a failure indicationthat the TB is not to be retransmitted autonomously from the terminaldevice.
 37. The method according to any of claims 30 to 36, wherein thescheduling policy comprises one or more of: scheduling priority for theTB; parameters for physical downlink control channel, PDCCH, carrying anuplink grant for retransmission of the TB; physical uplink sharedchannel, PUSCH, duration length for the TB; transmission powerparameters for the TB; and PUSCH preparation delay for the TB.
 38. Themethod according to any of claims 30 to 37, further comprising:transmitting (501), to a terminal device, information indicating apredetermined maximum number of transmission attempts or a predeterminedmaximum time period; and wherein the autonomous retransmission of a TBstops when the predetermined maximum number of transmission attempts isreached or the predetermined maximum time period has elapsed.
 39. Themethod according to claim 38, wherein the predetermined maximum numberof transmission attempts or the predetermined maximum time period isbased on a latency requirement of related service data or related one ormore logical channels.
 40. A terminal device (600) comprising: at leastone processor (610); and at least one memory (620), the at least onememory (620) containing instructions executable by the at least oneprocessor (610), whereby the terminal device (600) is operative to:transmit a transport block, TB, to a network node with a firstconfigured grant; and retransmit the TB to the network node autonomouslywith a second configured grant.
 41. The terminal device (600) accordingto claim 40, wherein the terminal device (600) is operative to performthe method according to any of claims 2 to
 29. 42. A network node (600)comprising: at least one processor (610); and at least one memory (620),the at least one memory (620) containing instructions executable by theat least one processor (610), whereby the network node (600) isoperative to: receive, from a terminal device, information related toone or more autonomous uplink retransmissions of a transport block, TB,with one or more configured grants; and determine a scheduling policy ora scheduling decision for the TB based on the information.
 43. Thenetwork node (600) according to claim 42, wherein the network node (600)is operative to perform the method according to any of claims 31 to 39.44. A method implemented in a communication system including a networknode and a terminal device, comprising: at the terminal device,transmitting (102) a transport block, TB, to the network node with afirst configured grant; at the terminal device, retransmitting (104) theTB to the network node autonomously with a second configured grant; atthe network node, receiving (502), from the terminal device, informationrelated to one or more autonomous uplink retransmissions of the TB withone or more configured grants; and at the network node, determine (504)a scheduling policy or a scheduling decision for the TB based on theinformation.
 45. A communication system comprising: a terminal deviceconfigured to transmit a transport block, TB, to the network node with afirst configured grant, and retransmit the TB to the network nodeautonomously with a second configured grant; and a network nodeconfigured to receive, from the terminal device, information related toone or more autonomous uplink retransmissions of the TB with one or moreconfigured grants, and determine a scheduling policy or a schedulingdecision for the TB based on the information.
 46. A computer readablestorage medium comprising instructions which when executed by at leastone processor, cause the at least one processor to perform the methodaccording to any of claims 1 to 39.